How do you handle Prisma migrations in a CI/CD pipeline?
Use prisma migrate dev for local development — it creates migration files and applies them. Use prisma migrate deploy in CI/CD — it applies only pending migrations without modifying the schema or resetting data. Always commit migration files to version control.
Prisma migration commands for dev and production
Migration workflow rules:
prisma migrate dev — development only; can reset the database on schema conflicts; never use in production.
prisma migrate deploy — production and CI; applies only pending migrations; never destructive.
Always commit migration SQL files to version control — they are the schema change history.
Run prisma generate in CI after deploying to regenerate the typed Prisma Client.
Use prisma migrate status in health checks to verify the database is in sync with the code.